@Fryguy I fixed the conflicts here if you can review again when you have time

Why is popper added directly. That is, won't it just come in naturally as a dependency?

Why is popper added directly. That is, won't it just come in naturally as a dependency?

When I try to run npm start without the popper package in the package.json it throws this error. I'm assuming because it's a peer dependency we need to actually declare it in the package.json.

ok, so from what I understand - the better way to declare missing peer dependencies is to use packageExtensions. This allows you to essentially force bootstrap to pull in the dependency (and we don't have to declare it as "our" dependency.

So in the .yarnrc.yml you would add something like:

packageExtensions:
  "bootstrap@*":
    dependencies:
      "popper.js": "~1.16.1"

This pull request is not mergeable. Please rebase and repush.

@Fryguy I fixed the dependency issue if you can review this again when you get a chance.

Checked commit GilbertCherrie@d82b19d with ruby 3.1.5, rubocop 1.56.3, haml-lint 0.62.0, and yamllint
1 file checked, 1 offense detected

**

• 💣 💥 🔥 🚒 - Linter/Yaml - missing config files

@Fryguy I think this pr is good to merge if you can review

@elsamaryv please review